Network management for content broadcast

ABSTRACT

Providing integrated LTE-B network and service management is disclosed. Changes to an LTE or LTE-B network can be propagated in real-time, or near-real-time, to a mapping profile representative of the LTE or LTE-B network. This mapping profile can be employed in updating the LTE or LTE-B network. Further, the mapping profile can be employed in establishing a new LTE-B session, adapting an existing LTE-B session, maintaining an existing LTE-B session, etc. Access to a reporting rule can enable the LTE or LTE-B network to proactively report changes to the LTE or LTE-B network. Integrated LTE-B network and service management can be integrated and/or centralized, such as, at a carrier-network, core-component. Moreover, integrated LTE-B network and service management can be virtualized.

RELATED APPLICATION

The subject application is a continuation of, and claims priority to,U.S. patent application Ser. No. 14/825,119, filed 12 Aug. 2015, andentitled “NETWORK MANAGEMENT FOR CONTENT BROADCAST,” the entirety ofwhich application is hereby incorporated by reference herein.

TECHNICAL FIELD

The disclosed subject matter relates to management of a networkassociated with broadcast of content, e.g., content from a long termevolution (LTE) broadcast (LTE-B) network(s) or enhanced multimediabroadcast multicast service (eMBMS) network(s).

BACKGROUND

By way of brief background, conventional multimedia broadcast multicastservice (MBMS) is generally reliant on determining individual bearerpaths to carry content from a service to a consuming device. Further,these services are typically implemented in a proprietary and/orstandalone manner without coordination between the providers of the MBMSservices. The bearer paths are frequently manually updated and often donot reflect up-to-date network topologies, e.g., the proprietary systemsfail to effectively learn the dynamics of the radio access and corenetwork elements expansion as well as the resulting network topologychanges via conventional interfaces.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of an example system that facilitates networkmanagement for content broadcast in accordance with aspects of thesubject disclosure.

FIG. 2 is a depiction of an example system that facilitates networkmanagement for content broadcast for multiple broadcast service areas inaccordance with aspects of the subject disclosure.

FIG. 3 illustrates an example system that facilitates network managementfor content broadcast via an integrated network and service managementlayer in accordance with aspects of the subject disclosure.

FIG. 4 illustrates an example system that facilitates network managementfor content broadcast via data exchange with an LTE management system inaccordance with aspects of the subject disclosure.

FIG. 5 illustrates an example system facilitating network management forcontent broadcast for a plurality of LTE service areas with topologyreporting rules in accordance with aspects of the subject disclosure.

FIG. 6 illustrates an example method facilitating network management forcontent broadcast in accordance with aspects of the subject disclosure.

FIG. 7 depicts an example method facilitating network management forcontent broadcast subject to topology reporting rules in accordance withaspects of the subject disclosure.

FIG. 8 illustrates an example method facilitating reporting topology viaa device of an LTE network and receiving network managed broadcastcontent for delivery in response to reporting topology in accordancewith aspects of the subject disclosure.

FIG. 9 depicts an example schematic block diagram of a computingenvironment with which the disclosed subject matter can interact.

FIG. 10 illustrates an example block diagram of a computing systemoperable to execute the disclosed systems and methods in accordance withan embodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

Conventional multimedia broadcast multicast service (MBMS) can bereliant on determining individual bearer paths to carry content from aservice to a consuming device. Further, conventional MBMS techniques,often associated with 3GPP technologies, are being similarly applied inlong term evolution (LTE) technologies, e.g., as enhanced MBMS (eMBMS)or LTE-Broadcast (LTE-B), without resolution of the issues that areoften associated with the poor deployment of MBMS services. Theseservices, e.g., MBMS and eMBMS, are typically proprietary standaloneservices lacking coordination between the proprietary providers. MBMSgenerally lacks automation and, as such, MBMS systems often do notreflect up-to-date network topologies because the proprietary systemsfail to learn the dynamics of the radio access and core network elementsas well as network topology changes via conventional interfaces. Ofnote, the term MBMS, eMBMS, and LTE-B, can each generally be usedinterchangeably in the present disclosure, except where specificallyrecited to illustrate a distinction from other technologies as will beappreciable to those of skill in the relevant arts.

In contrast to conventional proprietary systems for each contentdelivery service, unified network management can be implemented, e.g.,by a carrier network in core-network components, etc., to better reflectthe topology of a network for delivery of content. Unified networkmanagement can comprise real-time or near-real-time analysis of atopology of an LTE network associated with broadcasting content to aservice area. Moreover, unified network management can employ theanalysis of one or more LTE networks, or portions thereof, associatedwith broadcast delivery to one or more service areas. As such, broadcastcontent providers can expect that bearer paths to user equipments (UEs)can be kept up to date and can therefore better provide reliable contentdelivery to one or more UEs in one or more service areas in comparisonto conventional techniques. In part, conventional techniques can faildue to the complex mesh of network devices that can provide broadcastcontent delivery to a service area and the dynamic nature of thesecomplex networks, for example, in self-organizing networks, especiallythose comprising small cell eNodeBs (eNBs), Wi-Fi access points (APs),etc., the devices comprising the network can be in nearly constant fluxin some service areas, such as when mobile devices that are moving arealso acting as APs. Where broadcast content delivery systems are notupdated frequently enough as to changes in the devices comprising thedelivery network, there can be significant failures to actually deliverbroadcast content, e.g., routing data to edge devices that have left aservice area, edge devices that are highly burdened, edge devices thatare off-line, etc. A benefit of unified network management is that itcan, in some embodiments be tightly integrated to topology reporting,e.g., subject to topology reporting rules, in close communication withLTE network management systems, having carrier-level access to LTE-Bnetwork components such as broadcast/multicast service center (BMSC)components, media gateway (MGW) components, mobility management entity(MME) components, eNBs, and even to UEs on a carrier-network.

In an aspect, carrier networks can enable a centralized LTE-B corenetwork architecture design, wherein, for example, a BMSC component anda MGW component can be connected in a paired mode to connect toincumbent MME regional pools, e.g., one or more MME component, servingone or more LTE radio access network (RAN) nodes to facilitate provisionof high-speed mobility services comprising broadcast content. While notall MME components within a regional pool, or across one or moreregional pools, and their respective serving RAN nodes may be eMBMSenabled during the initial broadcast service deployment phase, legacyMBMS service can be integrated into LTE-B service architectures to allowbroadcast of content to network areas served by current and legacytechnologies. A BMSC component can be provisioned and managed by asingle service platform, or multiple platforms in other embodiments,that can be independent from a regional network management platform thatmanages the rest of the LTE-B network elements (including eNB, MME, MGW,S/P-GW, etc.). In an aspect, a service platform and a regional networkmanagement system(s) can be aware of an underlying network topologydesign via configuration management synchronization. Access to the BMSCcomponent to enable broadcast content delivery can be made available tocontent providers while management of the LTE-B network can be providedas a service by a carrier associated with the carrier-network LTEcomponents.

A regional network management system can manage the MGW, MME region, andassociated serving eNBs, to build a MBMS service configurationmanagement profile, e.g., embedded within a portal, that can enablereporting of topology related information to the BMSC such that the BMSCcan be aware of the downstream network topology when establishing MBMSsessions. Moreover, the regional network management system can managethese components for one or more BMSCs and/or one or more service areasassociated with the one or more BMSCs. In view of the BMSC being managedby a service management platform, it can derive the MGW Hostname,Destination Realm MME Interface IP addressing, service areaidentification (SAI), etc., to be able to successfully setup a MBMSsessions with appropriate downstream nodes. In some embodiments,regional systems can provide updated network constructs in real-time, ornear-real-time, to the service management platform for it to build aunified overall topology view of the network in real-time ornear-real-time. Changes in nodal configuration, construction of a MBMSmapping profile, and making the mapping profile available to a BMSCservice platform can therefore also be done in real-time ornear-real-time. The service provisioning platform can in turn update theMBMS mapping profile within the BMSC so that it can establish newsessions due to topology changes while simultaneously maintaining otherongoing sessions and MBMS bearer contexts in a manner that adapts tochanges in the LTE-B network topology.

In an aspect, LTE-B architecture as disclosed herein can be utilized foreffective broadcast content delivery, e.g., video services delivery,etc., over the same LTE infrastructure network while preserving scarcespectrum resources. In an aspect, emergency broadcasts that span acrossthe entire MBMS coverage area, e.g., SAI=0, the updated network topologywithin the herein disclosed BMSC can help to ensure that all downstreamnodes participating in the LTE-B are able to establish an MBMS sessionsuccessfully towards the eNBs so as to receive the emergency broadcastcontent. In another aspect, for a single BMSC-MGW design servingmultiple regional MME pools, the BMSC-MGW-MME connectivity and networktopology discovery can facilitate an accurate mapping profile defined inthe BMSC such that the MBMS session establishments affect traditionalLTE mobility services such as data, voice over LTE (VoLTE), E911 etc.,served by the MME regional pools, less adversely than they mightotherwise be. Additionally, in some embodiments, regional networkmanagement systems can be synchronized when reporting their respectiveMBMS mapping profiles to a centralized service management platform thatcan then use that mapping to provision the integrated MBMS profilewithin the BMSC.

The presently disclosed subject matter also illustrates, in someembodiments, a proactive approach in reporting such networkconfiguration dynamics to a service management platform over, such as astandardized interface like NETCONF/YANG, using a common message format,e.g., XML, these systems can apply topology reporting rules that canlead to increased certainty as to the accuracy of a mapping profile incomparison to the service platform trying to extract that informationfrom each of the regional network management systems that can beassociated with delay, errors, and failures to report for a myriad ofreasons, such as high latency, lost packets, etc. Moreover, auditing canbe employed to provide a feedback mechanism to improve capturing ofnetwork dynamics via the disclosed mapping of the network topology.

To the accomplishment of the foregoing and related ends, the disclosedsubject matter, then, comprises one or more of the features hereinaftermore fully described. The following description and the annexed drawingsset forth in detail certain illustrative aspects of the subject matter.However, these aspects are indicative of but a few of the various waysin which the principles of the subject matter can be employed. Otheraspects, advantages and novel features of the disclosed subject matterwill become apparent from the following detailed description whenconsidered in conjunction with the provided drawings.

FIG. 1 is an illustration of a system 100, which facilitates networkmanagement for content broadcast in accordance with aspects of thesubject disclosure. System 100 can comprise LTE-B network managementcomponent 110. LTE-B network management component 110 can send andreceive information with LTE-B network 190 or components thereof. In anaspect, LTE-B network management component 110 can receive informationrelated to the state of LTE-B network 190. This information can comprisetopology information, provisioning information, fault information,performance information, traffic information, resource(s) utilizationinformation, historical information, etc. As an example, LTE-B networkmanagement component 110 can receive information relating to thetopology of LTE-B network 190 and information indicating SAI(s) havingsome coverage via edge devices of LTE-B network 190, e.g., eNB(s)coverage areas. As another example, LTE-B network management component110 can receive information indicating that a MME component 164 isscheduled to be offline for service/repair at a future date/time, suchthat this information can be employed in determining a topology mappingprofile associated with said date/time that reflects a lower ranking ofthe MME component 164 and a higher ranking for other MME components 164to maintain broadcast coverage to service areas that would normally beserved by the MME component 164 expected to be offline. As a furtherexample, LTE-B network management component 110 can receive informationindicating that an eNB component 166 is highly burdened such that analternative eNB 166 can be selected, e.g., via a mapping profile, toenable establishment of a new MBMS session or maintenance or an existingMBMS session in the service area of the burdened eNB 166, e.g., trafficbalancing and load shifting can be enabled for LTE-B. As a still furtherexample, newly added, or deleted, smallcells (not illustrated, e.g.,femtocells, picocells, etc.) can be reflected in a topology map whereininformation related to the addition or removal of the smallcells isreceived from LTE-B network 190 by LTE-B network management component110.

In some embodiments, LTE-B network management component 110 can becomprised in a carrier network core-network. Whereas a carrier-networkoperating an LTE network has ready access to the types of informationdisclosed herein, this information can be communicated to LTE-B networkmanagement component 110 by core-network components of the carriernetwork. This can aid the carrier associated with the carrier network toact as a service provider to content broadcasters by providingbroadcasters access to an integrated network and service managementlayer, e.g., the broadcaster can provide service information to theintegrated network and service management layer which can then establisha session(s) on behalf of the broadcaster allowing content to bebroadcast to a UE without the broadcaster needing to directly managenetwork component routing.

LTE-B network management component 110 can also communicate informationto LTE-B network 190 and/or components thereof. In an aspect, LTE-Bnetwork management component 110 can adapt the configuration of LTE-Bnetwork 190. In an embodiment LTE-B network management component 110 canmanage LTE-B network 190 in response to information received by LTE-Bnetwork management component 110 from LTE-B network 190. As an example,LTE-B network management component 110 can direct alterations to thetopology of LTE-B network 190 to, for example, move UE 168 sessions froma first burdened eNB to another less burdened eNB in response toreceiving information from LTE-B network 190 that the first eNB isburdened. As another example, LTE-B network management component 110 canrestrict eMBMS through a newly added network edge device, e.g., a newlyadded Wi-Fi AP, etc., until a history of effective service has beenestablished. As a further example, LTE-B network management component110 can restrict eMBMS through a network edge device, e.g., a smallcell,etc., based on historical information reflecting spotty eMBMS service,in some instances, LTE-B network management component 110 can remove aspotty edge device from the LTE-B network, although it may remain in anLTE network for purposes other than MBMS content broadcasts.

LTE-B network management component 110 can be communicatively coupled toLTE-B service management component 120. LTE-B service managementcomponent 120 can receive information from LTE-B network managementcomponent 110. In an embodiment, this information can include topologyinformation related to LTE-B network 190. In an aspect, the topologyinformation can be simply passed through LTE-B network managementcomponent 110 to LTE-B service management component 120 withoutalteration, e.g., for analysis at LTE-B service management component120. In another aspect, LTE-B network management component 110 canperform analysis of, and/or operations of information received fromLTE-B network 190 to provide a mapping profile of LTE-B network 190,which, in some instances can reflect the real-time, or near-real-time,state of LTE-B network 190.

LTE-B service management component 120 can determine establishment ofLTE-B sessions based on the information received from LTE-B networkmanagement component 110. In some embodiments, additional informationcan also be included in demining LTE-B session establishment,provisioning, maintenance/updating of existing sessions, etc. As anexample, LTE-B service management component 120 can receive broadcastcontent 102, e.g., via LTE-B network 190 as illustrated, by a split feed(not illustrated), etc., and can analyze broadcast content 102 forcompliance with one or more rules. These rules can relate to encoding,resolution, content restrictions, content classification and/orprioritization, content duration, rights to broadcast the content, ornearly any other aspect related to the content. In an example, broadcastcontent 102 can be determined, by LTE-B service management component120, to comprise copyrighted material without a license or permission tobroadcast the copyrighted material, whereby LTE-B service managementcomponent 120 can restrict establishing LTE-B sessions in accord withreducing piracy of content. In a further example, objectionable orillegal content can be restricted, e.g., child pornography,dissemination of classified materials, etc. In another example, LTE-Bservice management component 120 can determine what regions are allowedaccess to broadcast content 102 and can adapt LTE-B sessionsaccordingly. In a further example, based on LTE-B network 190 topologymap received from LTE-B network management component 110 and informationrelated to broadcast content 102, LTE-B sessions can be adapted toincrease the quality of delivered content in underutilized LTE-Bnetworks or to restrict the quality of delivered content in burdenedLTE-B networks, in accord with customer agreements for both the providerof the broadcast content 102 and the customers associated with UE(s)168, e.g., via customer profile information communicated to LTE-Bservice management component 120, etc.

As LTE-B networks, e.g., 190, etc., become more ubiquitous and ofincreasing complexity, management of the LTE-B network, e.g., by LTE-Bnetwork management component 110, and of the LTE-B services, e.g., byLTE-B service management component 120, becomes increasingly relevant incontrast to conventional techniques that are generally proprietary. Asan example, conventional techniques of MBMS can result in numerousvertically integrated broadcast services that each require separatemaintenance and updating, which can actually increase backend trafficassociated with the LTE-B network, e.g., 190, receiving requests fortopology information from numerous broadcast services, replying to eachof those proprietary broadcast services, and little ability to adapt theLTE-B network itself, e.g., 190, in response to competing requests fromthe plurality of broadcast services. In contrast, the presentlydisclosed subject matter provides for a common point of entry into anLTE-B network, e.g., 190, for a plurality of broadcast services, whereinthe maintenance and management of the LTE-B network is not performed bynumerous competing broadcast services. Moreover, content itself can playa role in MBMS session establishment or maintenance, allowing foreffective quality control with regard to the broadcast content, e.g.,102. This can aid in effective dissemination of the broadcast contentthat accords with the condition of the LTE-B network, e.g., 190, as wellas customer agreements, service provider agreements, etc., piracyprotection, restrictions based on the subject matter of the broadcastcontent, e.g., illegal and/or immoral materials, etc.

In some embodiments, components of system 100 can be tightly integratedinto systems associated with the control and management of an LTEnetwork, e.g., carrier network core-components. Given that carriersalready manage LTE networks, it can readily be appreciated thatmanagement of LTE-B networks and service is highly complementary.Moreover, carriers can virtualize components into their core-networksallowing for highly flexible deployments, such as providing mobilevirtual network operators (MVNOs) to deploy separate instances of anLTE-B service that can be tailored to the MVNO while still remainingresponsive to LTE-B network analysis, network management, servicemanagement, etc.

In some embodiments, multiple broadcast content providers can introducecontent, e.g., 102, to LTE-B network 190 in conjunction with managementof the LTE-B network, e.g., by LTE-B network management component 110,and management of the LTE-B services, e.g., by LTE-B service managementcomponent 120. The several content packages, or streams, can be routedto the correct service areas for each stream in a manner that istypically more efficient and more fault tolerant than several discreteproprietary MBMS providers. In an aspect, LTE-B service managementcomponent 120 can receive LTE-B network 190 management information fromLTE-B network management component 110, and can then facilitateestablishment of new sessions or updating existing sessions based on theinformation received from LTE-B network management component 110 in viewof the several individual content streams. This clearly reduces theredundancy of components associated with deploying multiple proprietarysystems on top of an LTE network in an effort to accomplish similarresults.

FIG. 2 is a depiction of a system 200 that can facilitate networkmanagement for content broadcast for multiple broadcast service areas inaccordance with aspects of the subject disclosure. System 200 cancomprise LTE-B network management component 210. LTE-B networkmanagement component 210 can send and receive information with LTE-Bnetwork 290 and/or 291, or components thereof. In an aspect, LTE-Bnetwork management component 210 can receive information related to thestate of LTE-B networks 290 and 291. This information can comprisetopology information, provisioning information, performance information,traffic information, utilization information, historical information,etc., for the respective LTE-B networks, e.g., 290 or 291. As anexample, LTE-B network management component 210 can receive informationrelating to the topology of LTE-B network 290 and similarly receiveinformation indicating SAI(s) having some coverage via edge devices ofLTE-B network 291, e.g., eNB(s) coverage areas. As a further example,newly added, or deleted, smallcells (not illustrated) can be reflectedin one or more topology maps wherein information related to the additionor removal of the smallcells is received from LTE-B network 290 and/orLTE-B network 291 by LTE-B network management component 210.

In some embodiments, LTE-B network management component 210 can becomprised in a carrier network core-network. Whereas a carrier-networkoperating an LTE network can have ready access to the types ofinformation disclosed herein, this information can be communicated toLTE-B network management component 210 by core-network components of thecarrier network, e.g., in lieu of receiving said information directlyfrom LTE-B network 290 or 291. This can aid the carrier associated withthe carrier network in acting as a service provider to contentbroadcasters by providing broadcasters access to an integrated networkand service management layer, e.g., the broadcaster can provide serviceinformation to the integrated network and service management layer whichcan then establish a session(s) on behalf of the broadcaster allowingcontent to be broadcast to a UE without the broadcaster needing todirectly manage network component routing.

LTE-B network management component 210 can also communicate informationto LTE-B network(s) 290 and/or 291, and components thereof. In anaspect, LTE-B network management component 210 can adapt theconfiguration of LTE-B network 290 and/or LTE-B network 291. In anembodiment LTE-B network management component 210 can manage LTE-Bnetwork 290 in response to information received by LTE-B networkmanagement component 210 from LTE-B network 290 and simultaneouslymanage LTE-B network 291 in response to information received by LTE-Bnetwork management component 210 from LTE-B network 291.

LTE-B network management component 210 can be communicatively coupled toLTE-B service management component 220. LTE-B service managementcomponent 220 can receive information from LTE-B network managementcomponent 210. In an embodiment, this information can include topologyinformation related to LTE-B network 290. In an aspect, the topologyinformation can be simply passed through LTE-B network managementcomponent 210 to LTE-B service management component 220 withoutalteration, e.g., for analysis at LTE-B service management component220. In another aspect, LTE-B network management component 210 canperform analysis of, and/or operations on information received fromLTE-B network 290 and/or 291 to provide a mapping profile of LTE-Bnetwork 290 and/or 291 respectively, which, in some instances canreflect the real-time, or near-real-time, state of LTE-B network 290. Insome embodiments, LTE-B network management component 210 can performanalysis of, and/or operations on information received from LTE-Bnetwork 290 and 291 to provide a mapping profile of LTE-B network 290and 291 as a unified map, rather than as separate maps. LTE-B servicemanagement component 220 can also receive information from LTE-Bnetworks 290 and/or 291.

LTE-B service management component 220 can determine establishment ofLTE-B sessions based on the information received from LTE-B networkmanagement component 210. In some embodiments, additional informationcan also be included in demining LTE-B session establishment,provisioning, maintenance/updating of existing sessions, etc. As anexample, LTE-B service management component 220 can receive broadcastcontent 202, 203, etc., e.g., via LTE-B network 290 and/or 291 asillustrated, by a split feed (not illustrated), etc., and can analyzebroadcast content 202, 203, etc., for compliance with one or more rules.These rules can relate to encoding, resolution, content restrictions,content classification and/or prioritization, content duration, rightsto broadcast the content, or nearly any other aspect related to thecontent. In an example, broadcast content 202 can be determined, byLTE-B service management component 220, to comprise copyrighted materialwithout a license or permission to broadcast the copyrighted material,whereby LTE-B service management component 220 can restrict establishingLTE-B sessions in accord with reducing piracy of content, whilesimultaneously allowing establishment of sessions for broadcast content203. In an embodiment, system 200 can provide for broadcast of broadcastcontent 202 via LTE-B network 291 and correspondingly can enablebroadcast of broadcast content 203 via LTE-B network 290. This can beaccomplished by routing content between LTE-B networks, e.g., 290 and291. In other embodiments, broadcast content 202 and 203 can berestricted to either LTE-B network 290 or 291. As an example, whilebroadcast content 202 is illustrated as being introduced to LTE-Bnetwork 290, broadcast content 202 can be routed to LTE-B network 291such that broadcast content 202 and 203 are both broadcast through LTE-Bnetwork 291 and neither is broadcast through LTE-B network 290. Thisillustrates the highly adaptive nature of employing a centralized LTE-Bnetwork and service management architecture that would typically not beattainable in conventional systems that employ individual proprietaryLTE-B broadcast networks.

As LTE-B networks, e.g., 290, 291, etc., become more ubiquitous and ofincreasing complexity, management of the LTE-B network, e.g., by LTE-Bnetwork management component 210, and of the LTE-B services, e.g., byLTE-B service management component 220, becomes increasingly relevant incontrast to conventional techniques that are generally proprietary. Asan example, conventional techniques of MBMS can result in numerousvertically integrated broadcast services that each require separatemaintenance and updating, which can actually increase backend trafficassociated with the LTE-B network, e.g., 290, 291, etc., receivingrequests for topology information from numerous broadcast services,replying to each of those proprietary broadcast services, and littleability to adapt the LTE-B network itself, e.g., 290, 291, etc., inresponse to competing requests from the plurality of broadcast services.In contrast, the presently disclosed subject matter provides for one ormore common points of entry into one or more LTE-B networks, e.g., 290,291, etc., for a plurality of broadcast services, wherein themaintenance and management of the LTE-B network is not performed bynumerous competing broadcast services. Moreover, content itself can playa role in MBMS session establishment or maintenance, allowing foreffective quality control with regard to the broadcast content, e.g.,202, 203, etc. This can aid in effective dissemination of the broadcastcontent that accords with the condition of an LTE-B network, e.g., 290,291, etc., as well as customer agreements, service provider agreements,etc., piracy protection, restrictions based on the subject matter of thebroadcast content, e.g., illegal and/or immoral materials, etc.

In some embodiments, components of system 200 can be tightly integratedinto systems associated with the control and management of an LTEnetwork, e.g., carrier network core-components. Given that carriersgenerally already manage one or more LTE networks, it can readily beappreciated that management of LTE-B networks, e.g., 290, 291, etc., andbroadcast content service(s) is highly complementary. Moreover, carrierscan virtualize components into their core-networks allowing for highlyflexible deployments while still remaining responsive to LTE-B networkanalysis, network management, service management, etc.

In some embodiments, multiple broadcast content providers can introducecontent, e.g., 202, 203, etc., to LTE-B network(s) 290, 291, etc., inconjunction with management of the LTE-B network, e.g., by LTE-B networkmanagement component 210, and management of the LTE-B services, e.g., byLTE-B service management component 220. The several content packages, orstreams, e.g., those comprised in each of 202, 203, etc., can be routedto the correct service areas for each stream in a manner that istypically more efficient and more fault tolerant than several discreteproprietary MBMS providers. In an aspect, LTE-B service managementcomponent 220 can receive LTE-B network 290, 291, etc., managementinformation from LTE-B network management component 210, and can thenfacilitate establishment of new sessions or updating existing sessionsbased on the information received from LTE-B network managementcomponent 210 in view of the several individual content streams acrossbroadcast content(s) 202, 203, etc. This can reduce the redundancy ofcomponents associated with deploying multiple proprietary systems on topof an LTE network in an effort to accomplish similar results.

FIG. 3 illustrates a system 300 that facilitates network management forcontent broadcast via an integrated network and service management layerin accordance with aspects of the subject disclosure. System 300 cancomprise integrated network and service management layer component 330.Integrated network and service management layer component 330 canfurther comprise LTE-B network management component 310 and LTE-Bservice management component 320. Integrated network and servicemanagement layer component 330 can therefore send and receiveinformation with an LTE-B network, or components thereof, e.g., networktopology information 392, etc. In an aspect, integrated network andservice management layer component 330 can receive information relatedto the state of one or more LTE-B network. This information can comprisetopology information, provisioning information, performance information,traffic information, utilization information, historical information,etc., as disclosed herein in conjunction with LTE-B network managementcomponent 310, etc.

In some embodiments, integrated network and service management layercomponent 330 can also communicate information to one or more LTE-Bnetworks and/or components thereof, etc., e.g., network topology updateinformation 394, content routing information 360, broadcast content 304,etc. This can facilitate adapting a configuration of an LTE-B network.In an embodiment, integrated network and service management layercomponent 330 can manage an LTE-B network in response to informationreceived by integrated network and service management layer component330 from said LTE-B network, etc.

In some embodiments, integrated network and service management layercomponent 330 can perform analysis of, and/or operations on networkinformation to provide a mapping profile of one or more LTE-B networks,which, in some instances can reflect the real-time, or near-real-time,state of an LTE-B network. In some embodiments, integrated network andservice management layer component 330 can perform analysis ofinformation received from a plurality of LTE-B networks to provide aunified mapping profile, rather than as separate mapping profiles forthe several LTE-B networks.

In an aspect, integrated network and service management layer component330 can determine establishment of LTE-B sessions based on theinformation received from one or more LTE-B networks. In someembodiments, additional information can also be included in determiningLTE-B session establishment, provisioning, maintenance/updating ofexisting sessions, etc. As an example, integrated network and servicemanagement layer component 330 can receive broadcast content 302, etc.,and can analyze broadcast content 302, etc., for compliance with one ormore rules. These rules can relate to encoding, resolution, contentrestrictions, content classification, rights to broadcast the content,or nearly any other aspect related to the content. In an embodiment,system 300 can provide for broadcast of broadcast content 302 via one ormore LTE-B networks simultaneously. This can be accomplished by routingcontent between LTE-B networks. This illustrates an aspect of the highlyadaptive nature of employing a centralized LTE-B network and servicemanagement architecture that would typically not be attainable inconventional systems that employ individual proprietary LTE-B broadcastnetworks.

Integrated network and service management layer component 330 can becomprised in a carrier network core-network. Whereas a carrier-networkoperating an LTE network can have ready access to the types ofinformation disclosed herein, this information can be communicated tointegrated network and service management layer component 330 bycore-network components of the carrier network, e.g., in lieu ofreceiving said information directly from an LTE-B network. This can aidthe carrier associated with the carrier network in acting as a serviceprovider to content broadcasters by providing broadcasters access to anintegrated network and service management layer, e.g., the broadcastercan provide service information to the integrated network and servicemanagement layer which can then establish a session(s) on behalf of thebroadcaster allowing content to be broadcast to a UE without thebroadcaster needing to directly manage network component routing. Insome embodiments, components of system 300 can be tightly integratedinto systems associated with the control and management of an LTEnetwork, e.g., carrier network core-components. Given that carriersgenerally already manage one or more LTE networks, it can readily beappreciated that management of LTE-B networks and broadcast contentservice(s) is highly complementary. Moreover, carriers can virtualizecomponents into their core-networks allowing for highly flexibledeployments while still remaining responsive to LTE-B network analysis,network management, service management, etc.

In some embodiments, multiple broadcast content providers can introducecontent, e.g., broadcast content 302, etc., to integrated network andservice management layer component 330 and, in conjunction withmanagement of the LTE-B network, e.g., by LTE-B network managementcomponent 310, and management of the LTE-B services, e.g., by LTE-Bservice management component 330, this content can then be passed to oneor more LTE-B networks, e.g., as broadcast content 304. In an aspect,broadcast content 302 can be the same as broadcast content 304. In otheraspect, integrated network and service management layer component 330can alter, delay, or otherwise modify broadcast content 302 intobroadcast content 304. As an example, content that does not satisfycontent rules can be removed, content can be transcoded, content can bethrottled or have the quality altered, content can be supplemented, etc.

FIG. 4 illustrates a system 400 that facilitates network management forcontent broadcast via data exchange with an LTE management system inaccordance with aspects of the subject disclosure. System 400 cancomprise integrated network and service management layer component 430.In some embodiments, integrated network and service management layercomponent 430 can further comprise LTE-B network management componentand LTE-B service management component, not illustrated for brevity andclarity. Integrated network and service management layer component 430can send and receive information with an LTE management layer component406 that can in turn send and receive information with an LTE network496, or components thereof, e.g., network topology information 492, etc.In an aspect, integrated network and service management layer component430 can receive information related to the state of one or more LTEnetwork. This LTE network information can comprise topology information,provisioning information, performance information, traffic information,utilization information, historical information. In an aspect, LTEnetwork 496 coupled with BMSC component 460 can act as an LTE-B networkas disclosed elsewhere herein, however system 400 illustrates them asseparated to emphasize that an LTE network, e.g., 496, etc., as canreadily be found in many carrier-network systems, can function as anLTE-B network with the addition of a BMSC component, e.g., 460, or othersimilar functionality embodied in other components. In some embodiments,integrated network and service management layer component 430 can alsocommunicate information to one or more LTE networks and/or componentsthereof, etc., non-illustrated for clarity and brevity. Access to LTEnetwork information can facilitate adapting the LTE network, e.g., 496,etc., directly (not illustrated) or via LTE management layer component406.

In some embodiments, integrated network and service management layercomponent 430 can perform analysis of, and/or operations on networkinformation to provide a mapping profile of one or more functional LTE-Bnetworks, e.g., LTE network 496 coupled to BMSC component 460, which, insome instances can reflect the real-time, or near-real-time, state of afunctional LTE-B network. In some embodiments, integrated network andservice management layer component 430 can perform analysis ofinformation received from a plurality of LTE networks, e.g., 496, etc.,to provide a unified mapping profile, rather than as separate mappingprofiles.

In an aspect, integrated network and service management layer component430 can determine establishment of functional LTE-B sessions, e.g.,those established on BMSC component 460 and LTE network 496, etc., basedon the information received from one or more LTE-B networks. In someembodiments, additional information can also be included in determiningLTE-B session establishment, provisioning, maintenance/updating ofexisting sessions, etc. As an example, integrated network and servicemanagement layer component 430 can receive broadcast content 402, etc.,and can analyze broadcast content 402, etc., for compliance with one ormore rules. These rules can relate to encoding, resolution, contentrestrictions, content classification and/or prioritization, contentduration, rights to broadcast the content, or nearly any other aspectrelated to the content. In an embodiment, system 400 can provide forbroadcast of broadcast content 402 via one or more functional LTE-Bnetworks simultaneously. This can be accomplished by routing contentbetween functional LTE-B networks, e.g., an LTE network coupled to BMSCcomponent 460.

In some embodiments, integrated network and service management layercomponent 430 can be comprised in a carrier network core-network.Whereas a carrier-network operating an LTE network, e.g., 496 via LTEmanagement layer component 406, can have ready access to the types ofinformation disclosed herein, this information can be communicated tointegrated network and service management layer component 430 bycore-network components of the carrier network, e.g., LTE managementlayer component 406. This can aid the carrier in acting as a serviceprovider to content broadcasters by providing broadcasters access to anintegrated network and service management layer, e.g., the broadcastercan provide service information to the integrated network and servicemanagement layer which can then establish a session(s) on behalf of thebroadcaster allowing content to be broadcast to a UE without thebroadcaster needing to directly manage network component routing. Insome embodiments, components of system 400 can be tightly integratedinto systems associated with the control and management of an LTEnetwork, e.g., LTE management layer component 406, etc. Given thatcarriers generally already manage one or more LTE networks, it canreadily be appreciated that management of functional LTE-B networks andbroadcast content service(s) is complementary. Moreover, carriers canvirtualize components into their core-networks allowing for highlyflexible deployments while remaining responsive to LTE-B network-typeanalysis, network management, service management, etc. In someembodiments, multiple broadcast content providers can introduce content,e.g., broadcast content 402, etc., to integrated network and servicemanagement layer component 430 and, in conjunction with management ofthe functional LTE-B network, this content can then be passed to one ormore LTE-B networks.

FIG. 5 illustrates a system 500 that facilitates network management forcontent broadcast for a plurality of LTE service areas with topologyreporting rules in accordance with aspects of the subject disclosure.System 500 can comprise integrated network and service management layercomponent 530. In some embodiments, integrated network and servicemanagement layer component 530 can further comprise LTE-B networkmanagement component and LTE-B service management component, notillustrated for brevity and clarity. Integrated network and servicemanagement layer component 530 can send and receive information with oneor more LTE management layer components, e.g., 506, etc., that can inturn send and receive information with one or more LTE networks 596,597, etc., or components thereof. In an aspect, integrated network andservice management layer component 530 can receive information relatedto the state of one or more LTE networks, e.g., 596, 597, etc. This LTEnetwork information can comprise topology information, provisioninginformation, performance information, traffic information, utilizationinformation, historical information. In an aspect, LTE network 596coupled with BMSC component 560 can act as an LTE-B network as disclosedelsewhere herein, and similarly, LTE network 597 coupled with BMSCcomponent 561 can act as another LTE-B network. In some embodiments,integrated network and service management layer component 530 can alsocommunicate information to one or more LTE networks and/or componentsthereof. Access to LTE network information can facilitate adapting anLTE network, e.g., 596, 597, etc.

In some embodiments, integrated network and service management layercomponent 530 can perform analysis of, and/or operations on networkinformation to provide one or more mapping profiles of one or morefunctional LTE-B networks, e.g., LTE network 596 coupled to BMSCcomponent 560, LTE network 597 coupled to BMSC component 561, etc.,which, in some instances can reflect the real-time, or near-real-time,state of a functional LTE-B network. In some embodiments, integratednetwork and service management layer component 530 can perform analysisof information received from a plurality of LTE networks, e.g., 596,597, etc., to provide a unified mapping profile, rather than as separatemapping profiles.

In an aspect, integrated network and service management layer component530 can determine establishment of functional LTE-B sessions, e.g.,those established on BMSC component 560 and LTE network 596, LTE network597 coupled to BMSC component 561, etc., based on the informationreceived from one or more LTE-B networks. In certain instances, BMSCcomponent 560 can further substitute for BMSC 561 with regard to forminga functional LTE-B network with LTE network 597. In some embodiments,additional information can also be included in determining LTE-B sessionestablishment, provisioning, maintenance/updating of existing sessions,etc. As an example, integrated network and service management layercomponent 530 can receive broadcast content 502, 503, etc., and cananalyze broadcast content 502, 503, etc., for compliance with one ormore rules. These rules can relate to encoding, resolution, contentrestrictions, content classification and/or prioritization, contentduration, rights to broadcast the content, or nearly any other aspectrelated to the content. In an embodiment, system 500 can provide forbroadcast of broadcast content 502, 503, etc., via one or morefunctional LTE-B networks simultaneously. This can be accomplished byrouting content between functional LTE-B networks, e.g., LTE network596, 597, etc., coupled to BMSC component 560, LTE network 596, 597,etc., coupled to BMSC component 561, etc.

In some embodiments, integrated network and service management layercomponent 530 can be comprised in a carrier network core-network.Whereas a carrier-network operating an LTE network, e.g., 596, 597,etc., via LTE management layer component 506, can have ready access tothe types of information disclosed herein, this information can becommunicated to integrated network and service management layercomponent 530 by core-network components of the carrier network, e.g.,LTE management layer component 506. This can aid the carrier in actingas a service provider to content broadcasters by providing broadcastersaccess to an integrated network and service management layer, e.g., thebroadcaster can provide service information to the integrated networkand service management layer which can then establish a session(s) onbehalf of the broadcaster allowing content to be broadcast to a UEwithout the broadcaster needing to directly manage network componentrouting. In some embodiments, components of system 500 can be tightlyintegrated into systems associated with the control and management of anLTE network, e.g., LTE management layer component 506, etc. Given thatcarriers generally already manage one or more LTE networks, it canreadily be appreciated that management of functional LTE-B networks andbroadcast content service(s) is complementary. Moreover, carriers canvirtualize components into their core-networks allowing for highlyflexible deployments while remaining responsive to LTE-B network-typeanalysis, network management, service management, etc. In someembodiments, multiple broadcast content providers can introduce content,e.g., broadcast content 502, 503, etc., to integrated network andservice management layer component 530 and, in conjunction withmanagement of the functional LTE-B network, this content can then bepassed to one or more LTE-B networks.

In an aspect, integrated network and service management layer component530 can further provide topology reporting rule 534, 535, etc., to LTEnetworks, e.g., 596, 597, etc. This topology reporting rule, e.g., 534,535, etc., can enable automatic reporting of topology information tointegrated network and service management layer component 530 by one ormore LTE networks, e.g., 596, 597, etc., or functional LTE-B networks.This can, for example, reduce network traffic associated with activelypolling for topology changes by providing a structure, e.g., a rule,under which LTE and/or LTE-B networks can self-monitor and report. Insome instances, topology reporting rule 534 can be the same as topologyreporting rule 535. In other instances, topology reporting rule 534 canbe different from topology reporting rule 535. Moreover, in someembodiments, topology reporting rule 534 can be communicated between LTEnetwork 597 and LTE network 596 via LTE management layer component 506,e.g., integrated network and service management layer component 530 cansource a topology reporting rule, which can then propagate to one ormore LTE networks, via other components of system 500.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 6-FIG. 8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 6 illustrates a method 600 facilitating network management forcontent broadcast in accordance with aspects of the subject disclosure.At 610, method 600 can comprise receiving network information. Networkinformation can comprise topology information, provisioning information,performance information, traffic information, utilization information,historical information, etc. This network information can facilitateadapting a configuration of an LTE-B network and/or determining aspectsof establishing new sessions or adapting existing sessions for broadcastof content on an LTE-B network.

At 620, method 600 can comprise determining multimedia broadcastmulticast service (eMBMS) mapping information. This can be based on thenetwork topology information and broadcast service information.Broadcast service information can comprise customer agreements, serviceprovider agreements, etc., piracy protection, restrictions based on thesubject matter of the broadcast content, e.g., illegal and/or immoralmaterials, etc. As such, the mapping can reflect aspects of the contentand aspects of the LTE-B network topology to provide a well-managedbroadcast delivery experience. In some embodiments, the eMBMS mappinginformation can be determined from the network topology informationprior to applying the broadcast service information to the mappinginformation as part of establishing, maintaining, or updating an LTE-Bsession, however this is not illustrated for the sake of clarity andbrevity, although it is well within the scope of the presently disclosedsubject matter.

At 630, network topology can be updated by method 600. The updating ofthe network topology can be based on the eMBMS mapping information. Inan embodiment an LTE-B network can be managed in response to informationreceived at 610 and/or determined at 620. As an example, alterations tothe topology of an LTE-B network can comprise, for example, moving a UEfrom a first burdened eNB to another less burdened eNB in response toreceiving information from that the first eNB is burdened. As anotherexample, routing information through a newly added network edge device,e.g., a newly added Wi-Fi AP, etc., can be restricted until a history ofeffective service has been established. As a further example, LTE-Btraffic through a network edge device, e.g., a femtocell, etc., can beincreased based on historical information reflecting excellent eMBMSservice.

At 640, system 600 can comprise enabling broadcast content delivery froma broadcast component to a UE. At this point Method 600 can end. Theenabling broadcast content delivery can be based on the EMBMS mappinginformation determined at 620. In an aspect, method 600 can provide forestablishing a new eMBMS session, maintaining an existing eMBMS session,updating an existing eMBMS session, etc., based on analysis of thenetwork information from 610 and the determined eMBMS mappinginformation from 620.

In an aspect, method 600 can provide for real-time, or near-real-time,correction for changes in an LTE-B network. Moreover, in someembodiments, method 600 can be employed in a carrier-networkcore-device. This can be highly efficient where a carrier-network isalready associated with management and control of an LTE network thatoperates as a portion of an LTE-B network. Moreover, centralization ofmethod 600 can allow broadcast content providers to avoid management ofnetwork components and to more simply rely on a carrier to providemanagement as a service on core-network components associated with thecarrier-network.

FIG. 7 illustrates a method 700 that facilitates network management forcontent broadcast subject to topology reporting rules in accordance withaspects of the subject disclosure. At 710, method 700 can compriseallowing access to an LTE network topology reporting rule. The LTEnetwork topology reporting rule can relate to conditions under which anLTE network component is directed to report topology information to anLTE-B network management component. These rules can reduce networkcontrol traffic by allowing LTE network components to determine when toreport topology information in accordance with one or more LTE networktopology reporting rule(s).

At 720, LTE network topology information can be received. The receivingof LTE network topology information can be in accord with the LTEnetwork reporting rule. This network topology information can comprisetopology information in conjunction with supplemental information, suchas, provisioning information, performance information, trafficinformation, utilization information, historical information, etc.Furthermore, the LTE network topology information can be associated withan LTE network, more specifically, an LTE network associated with anLTE-B or LTE network for carrying broadcast content.

At 730, method 700 can comprise determining LTE-B mapping information.The LTE-B mapping information can be based on the LTE network topologyinformation. In an aspect, the LTE-B mapping information can also bebased on broadcast service information, as disclosed elsewhere herein.In some embodiments, LTE-B mapping information can reflect thereal-time, or near-real-time, state of LTE-B network.

At 740, method 700 can comprise enabling broadcast content delivery froma broadcast component to a UE via the LTE network based on the LTE-Bmapping information. At this point method 700 can end. Establishment ofLTE-B sessions can be based on the LTE-B mapping information. In someembodiments, additional information can also be included in deminingLTE-B session establishment, provisioning, maintenance/updating ofexisting sessions, etc. As an example, broadcast content can be analyzedfor compliance with one or more rules, e.g., rules can relate toencoding, resolution, content restrictions, content classification,rights to broadcast the content, etc.

Method 700 can provide for one or more common points of entry into oneor more LTE-B networks, for one or more broadcast services, wherein themaintenance and management of the LTE-B network can be moved away fromnumerous competing broadcast services, and rather can be performed by anintegrated network and service management layer. In some embodimentsthis integrated network and service management layer can be embodied ina carrier-network core-network component. Moreover, content itself canplay a role in LTE-B session establishment or maintenance, allowing foreffective quality control with regard to the broadcast content. This canaid in effective dissemination of the broadcast content that accordswith the condition or state of an LTE-B network, e.g., the evolvingtopology of the LTE-B network, etc., as well as customer agreements,service provider agreements, etc., piracy protection, restrictions basedon the subject matter of the broadcast content, e.g., illegal and/orimmoral materials, etc., and simplifies and consolidates management ofthe LTE-B network by integrating and/or centralizing the componentsexecuting the method.

FIG. 8 illustrates a method 800 that facilitates reporting topology viaa device of an LTE network and receiving network managed broadcastcontent for delivery in response to reporting topology in accordancewith aspects of the subject disclosure. At 810, method 800 can comprisetriggering, by an LTE network device of an LTE network, a determinationof LTE network topology information. The LTE network topologyinformation can be associated with an LTE topology of the LTE network.Further, the LTE network serves a UE. In an aspect, an LTE-B network cancomprise components such as broadcast/multicast service center (BMSC)components, etc., and LTE network components, such as, media gateway(MGW) components, mobility management entity (MME) components, eNBs.Method 800 can be performed by any LTE network component or any LTE-Bnetwork component. In an aspect, the triggering can be based upon a rulereceived by the LTE or LTE-B component. A rule can be related toreporting changes in network topology, changes in conditions associatedwith elements of a network, etc. As an example, the addition of a Wi-FiAP or femtocell to a network can trigger the determining of LTE networktopology. As another example, historical characteristics of a networkcomponent can trigger the determining of the LTE network topology. Itwill be appreciated that numerous other network component conditions,states, transitions, etc., can trigger the determining of the LTEnetwork topology and these are expressly considered within the scope ofthe present disclosure although they are not enumerated here for thesake of clarity and brevity.

At 820, method 800 can comprise enabling access to the LTE networktopology information by the LTE network device. Access to the LTEnetwork topology information can be enabled for a component of a controlnetwork associated with a network carrier identity. Further, the accesscan facilitate the component of the control network determining an LTE-Bmap. In an aspect, this determining of the LTE-B map can be real-time ornear-real-time where the triggering of 810 and the access of 820 arealso real-time or near-real-time.

At 830, in response to the enabling access to the LTE network topology,method 800 can comprise receiving, the LTE network device, broadcastcontent and routing information. At this point method 800 can end. Therouting information can be employed for directing the broadcast contenttowards the UE and can be updated based on the LTE-B map.

Method 800 illustrates components or devices of an LTE networkinteracting with a control network component, e.g., a componentassociated with an integrated network and service management layer. Thisintegrated network and service management layer can be comprised in acarrier-network core-component.

FIG. 9 is a schematic block diagram of a computing environment 900 withwhich the disclosed subject matter can interact. The system 900comprises one or more remote component(s) 910. The remote component(s)910 can be hardware and/or software (e.g., threads, processes, computingdevices). In some embodiments, remote component(s) 910 can compriseservers, personal servers, wireless telecommunication network devices,etc. As an example, remote component(s) 910 can be LTE-B networkmanagement component 110, 210, 310 etc., LTE-B service managementcomponent 120, 220, 320, etc., integrated network and service managementlayer component 330, 430, 530, etc., LTE management layer component 406,506, etc.

The system 900 also comprises one or more local component(s) 920. Thelocal component(s) 920 can be hardware and/or software (e.g., threads,processes, computing devices). In some embodiments, local component(s)920 can comprise, for example, LTE-B network 190, 290, 291, etc., LTEnetwork 496, 596, 597, etc., BMSC component 160, 460, 560, 561, etc.,MGW component 162, MME component(s) 164, eNB component(s) 166, UE 168,etc.

One possible communication between a remote component(s) 910 and a localcomponent(s) 920 can be in the form of a data packet adapted to betransmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 910 and a local component(s)920 can be in the form of circuit-switched data adapted to betransmitted between two or more computer processes in radio time slots.The system 900 comprises a communication framework 940 that can beemployed to facilitate communications between the remote component(s)910 and the local component(s) 920, and can comprise an air interface,e.g., Uu interface of a UMTS network. Remote component(s) 910 can beoperably connected to one or more remote data store(s) 950, such as ahard drive, SIM card, device memory, etc., that can be employed to storeinformation on the remote component(s) 910 side of communicationframework 940. Similarly, local component(s) 920 can be operablyconnected to one or more local data store(s) 930, that can be employedto store information on the local component(s) 920 side of communicationframework 940.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules comprise routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can comprise both volatile and nonvolatilememory, by way of illustration, and not limitation, volatile memory 1020(see below), non-volatile memory 1022 (see below), disk storage 1024(see below), and memory storage 1046 (see below). Further, nonvolatilememory can be included in read only memory, programmable read onlymemory, electrically programmable read only memory, electricallyerasable read only memory, or flash memory. Volatile memory can compriserandom access memory, which acts as external cache memory. By way ofillustration and not limitation, random access memory is available inmany forms such as synchronous random access memory, dynamic randomaccess memory, synchronous dynamic random access memory, double datarate synchronous dynamic random access memory, enhanced synchronousdynamic random access memory, Synchlink dynamic random access memory,and direct Rambus random access memory. Additionally, the disclosedmemory components of systems or methods herein are intended to comprise,without being limited to comprising, these and any other suitable typesof memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, comprising single-processoror multiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,netbook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, part of, LTE-Bnetwork management component 110, 210, 310 etc., LTE-B servicemanagement component 120, 220, 320, etc., integrated network and servicemanagement layer component 330, 430, 530, etc., LTE management layercomponent 406, 506, etc., LTE-B network 190, 290, 291, etc., LTE network496, 596, 597, etc., BMSC component 160, 460, 560, 561, etc., MGWcomponent 162, MME component(s) 164, eNB component(s) 166, UE 168, etc.,comprises a processing unit 1014, a system memory 1016, and a system bus1018. System bus 1018 couples system components comprising, but notlimited to, system memory 1016 to processing unit 1014. Processing unit1014 can be any of various available processors. Dual microprocessorsand other multiprocessor architectures also can be employed asprocessing unit 1014.

System bus 1018 can be any of several types of bus structure(s)comprising a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures comprising, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 1194), and small computer systems interface.

System memory 1016 can comprise volatile memory 1020 and nonvolatilememory 1022. A basic input/output system, containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can compriseread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1020 comprises read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, Synchlink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1012 can also comprise removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 comprises, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can comprise storage media separately or in combination with otherstorage media comprising, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1024to system bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, read only memory, programmable readonly memory, electrically programmable read only memory, electricallyerasable read only memory, flash memory or other memory technology,compact disk read only memory, digital versatile disk or other opticaldisk storage, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or other tangible media which can beused to store desired information. In this regard, the term “tangible”herein as may be applied to storage, memory or computer-readable media,is to be understood to exclude only propagating intangible signals perse as a modifier and does not relinquish coverage of all standardstorage, memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can comprisenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium. As such, for example, a computer-readable medium can compriseexecutable instructions stored thereon that, in response to execution,cause a system comprising a processor to perform operations, comprising:receiving trigger information a remote device, e.g., a UE, and inresponse, generating communication augmentation information that can beaccessed via an air interface or other wireless interface by one or moreservice interface components or other UEs to enable context sensitivecommunication augmentation.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and comprises any informationdelivery or transport media. The term “modulated data signal” or signalsrefers to a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediacomprise wired media, such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software comprises an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. In some embodiments, a user interface can allowentry of user preference information, etc., and can be embodied in atouch sensitive display panel, a mouse input GUI, a command linecontrolled interface, etc., allowing a user to interact with computer1012. As an example, UI Component 252 can receive touch, motion, audio,visual, or other types of input. Input devices 1036 comprise, but arenot limited to, a pointing device such as a mouse, trackball, stylus,touch pad, keyboard, microphone, joystick, game pad, satellite dish,scanner, TV tuner card, digital camera, digital video camera, webcamera, cell phone, smartphone, tablet computer, etc. These and otherinput devices connect to processing unit 1014 through system bus 1018 byway of interface port(s) 1038. Interface port(s) 1038 comprise, forexample, a serial port, a parallel port, a game port, a universal serialbus, an infrared port, a Bluetooth port, an IP port, or a logical portassociated with a wireless service, etc. Output device(s) 1040 use someof the same type of ports as input device(s) 1036.

Thus, for example, a universal serial busport can be used to provideinput to computer 1012 and to output information from computer 1012 toan output device 1040. Output adapter 1042 is provided to illustratethat there are some output devices 1040 like monitors, speakers, andprinters, among other output devices 1040, which use special adapters.Output adapters 1042 comprise, by way of illustration and notlimitation, video and sound cards that provide means of connectionbetween output device 1040 and system bus 1018. It should be noted thatother devices and/or systems of devices provide both input and outputcapabilities such as remote computer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, a cloud service, code executing ina cloud-computing environment, a workstation, a microprocessor basedappliance, a peer device, or other common network node and the like, andtypically comprises many or all of the elements described relative tocomputer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies comprise fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring and the like. Wide areanetwork technologies comprise, but are not limited to, point-to-pointlinks, circuit-switching networks like integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines. As noted below, wireless technologies may be used inaddition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can comprise, for example, internaland external technologies such as modems, comprising regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, comprising what is described in the Abstract, is notintended to be exhaustive or to limit the disclosed embodiments to theprecise forms disclosed. While specific embodiments and examples aredescribed herein for illustrative purposes, various modifications arepossible that are considered within the scope of such embodiments andexamples, as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can comprise a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “eNodeB,” “home Node B,” “home accesspoint,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream to and from a set ofsubscriber stations or provider enabled devices. Data and signalingstreams can comprise packetized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks comprisebroadcast technologies (e.g., sub-Hertz, extremely low frequency, verylow frequency, low frequency, medium frequency, high frequency, veryhigh frequency, ultra-high frequency, super-high frequency, terahertzbroadcasts, etc.); Ethernet; X.25; powerline-type networking, e.g.,Powerline audio video Ethernet, etc.; femtocell technology; Wi-Fi;worldwide interoperability for microwave access; enhanced general packetradio service; third generation partnership project, long termevolution; third generation partnership project universal mobiletelecommunications system; third generation partnership project 2, ultramobile broadband; high speed packet access; high speed downlink packetaccess; high speed uplink packet access; enhanced data rates for globalsystem for mobile communication evolution radio access network;universal mobile telecommunications system terrestrial radio accessnetwork; or long term evolution advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: determininga change in network mapping for a long term evolution broadcast networkcurrently being for broadcasting enhanced multimedia broadcast multicastservice content, wherein the determining the change is based on networkinformation corresponding to a receiving device accessing the enhancedmultimedia broadcast multicast service content from a remotely locatedcontent provider device via a current broadcast session being enabled bya network device of the long term evolution broadcast network, andwherein the remotely located content provider device and the networkdevice do not comprise the processor and the memory; and based on thechange in the network mapping, adapting the current broadcast sessionresulting in an adapted broadcast session that facilitates accessing theenhanced multimedia broadcast multicast service content by the receivingdevice via the adapted broadcast session.
 2. The system of claim 1,wherein the adapting the current broadcast session is further based on acharacteristic of the enhanced multimedia broadcast multicast servicecontent.
 3. The system of claim 1, wherein the adapting the currentbroadcast session comprises establishing a new broadcast session.
 4. Thesystem of claim 1, wherein the adapting the current broadcast sessioncomprises modifying another existing broadcast session.
 5. The system ofclaim 1, wherein the adapting the current broadcast session comprisessuspending an established broadcast session.
 6. The system of claim 5,wherein the established broadcast session is the current broadcastsession.
 7. The system of claim 1, wherein the determining the change inthe network mapping is based on network mapping information at least inpart resulting from applying a reporting rule to network devicescomprising the network device that causes at least a portion of thenetwork devices to report corresponding network device conditions to thesystem.
 8. The system of claim 1, wherein the determining the change inthe network mapping occurs in response to a change in performance of thelong term evolution broadcast network.
 9. The system of claim 1, whereinthe processor is comprised in a core-network device associated with acarrier identity.
 10. A method, comprising: determining, by a systemcomprising a processor, a perturbation of a network map for a long termevolution broadcast network in active use for broadcasting enhancedmultimedia broadcast multicast service content, wherein the long termevolution broadcast network facilitates distribution of the enhancedmultimedia broadcast multicast service content from a source device toan edge device via a long term evolution broadcast session facilitatedby a network device in accordance with the network map, and wherein thesource device and the network device do not comprise the processor; andupdating, by the system, the long term evolution broadcast session inresponse to the determining the perturbation of the network map, whereinthe updating enables the edge device to access the enhanced multimediabroadcast multicast service content via an updated long term evolutionbroadcast session that replaces the long term evolution broadcastsession.
 11. The method of claim 10, wherein the updating the long termevolution broadcast session is further based on a characteristic of theenhanced multimedia broadcast multicast service content being broadcast.12. The method of claim 10, wherein the updating the long term evolutionbroadcast session comprises establishing a new long term evolutionbroadcast session to replace the long term evolution broadcast sessionbased on the perturbation of the long term evolution broadcast map. 13.The method of claim 10, wherein the updating the long term evolutionbroadcast session comprises terminating the long term evolutionbroadcast session based on the perturbation of the long term evolutionbroadcast map.
 14. The method of claim 10, wherein the updating the longterm evolution broadcast session comprises altering an existing longterm evolution broadcast session based on the perturbation of the longterm evolution broadcast map.
 15. The method of claim 14, wherein theexisting broadcast session is the long term evolution broadcast session.16. The method of claim 10, wherein the determining is performed in acore-network device associated with a carrier identity.
 17. Anon-transitory machine-readable storage medium comprising executableinstructions that, when executed by a processor facilitate performanceof operations, comprising: in response to determining a change to atopology of a long term evolution broadcast network being employed forbroadcasting enhanced multimedia broadcast multicast service content,determining updated long term evolution broadcast mapping informationbased on current long term evolution broadcast mapping informationrelating to enabling access to the enhanced multimedia broadcastmulticast service content from a source device to an edge device via along term evolution broadcast session employing a network device inaccordance with the current long term evolution broadcast mappinginformation, and wherein the source device and the network device do notcomprise the processor; and adapting the long term evolution broadcastsession based on the updated long term evolution broadcast mappinginformation, to facilitate the access to the enhanced multimediabroadcast multicast service content by the edge device via an updatedlong term evolution broadcast session that replaces the long termevolution broadcast session.
 18. The non-transitory machine-readablestorage medium of claim 17, wherein the updating the long term evolutionbroadcast session is further based on a characteristic of the enhancedmultimedia broadcast multicast service content being broadcast.
 19. Thenon-transitory machine-readable storage medium of claim 17, wherein theadapting the long term evolution broadcast session comprises at leastone of establishing a new long term evolution broadcast session based onthe updated long term evolution broadcast mapping information,terminating a long term evolution broadcast session based on the updatedlong term evolution broadcast mapping information, or adapting anexisting long term evolution broadcast session based on the updated longterm evolution broadcast mapping information.
 20. The non-transitorymachine-readable storage medium of claim 17, wherein the processor iscomprised in a core-network device associated with a carrier identity.